docs: refresh home stats for oxlint, vite, and vitest Issue: #1511#1512
Conversation
✅ Deploy Preview for viteplus-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
nozomee
changed the title
|
We want a way to automate the npm downloads & github stars. Otherwise the hard coded numbers will be outdated quickly. For example, vitest had 7% increase in downloads in the last week. A potential way to do this is to have a fetch data script that is executed on a schedule via github actions. The data is stored as a json in this repo, which the home pages references |
|
I’d like to take this on — I’m already actively working on it and will open a PR soon. Right now the trusted-stack numbers on the homepage are hard-coded, which means they’ll drift quickly and require repeated manual edits over time (especially with npm download velocity changing week-to-week). My planned implementation: Add a lightweight fetch script that pulls: Why this should help: Keeps homepage metrics current automatically Expected flow after merge: Merge once A few maintainer decisions may still be useful: Whether github-actions[bot] should push JSON-only updates directly to main or use PRs In short: automate the trusted-stack stats pipeline once, remove repetitive manual maintenance, and keep homepage credibility high with minimal long-term overhead. PR coming soon. |
|
@jong-kyung @mdong1909 I’ve committed the changes to address these updates, Kindly review it once! |
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 23b81b2815
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…o node-version-file: .node-version
|
@jong-kyung @mdong1909 I’ve committed the changes , Kindly review it once! |
…and TypeScript migration
|
@jong-kyung @camc314 I’ve committed the changes , Kindly review it once! |
|
@codex review |
|
Codex Review: Didn't find any major issues. Breezy! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
|
@nozomee Could you take a look at the failing CI? |
…ocs lockfile - Relocate fetch script to .github/scripts and update references - Fix docs deps (no catalog:), update docs pnpm-lock - Adjust docs scripts tsconfig for node/dom types
|
@jong-kyung I’ve committed the changes , Kindly review it once! |
- Update update-trusted-stack-stats workflow to use correct script path - Move stats typecheck tsconfig under .github/scripts and remove docs/scripts/tsconfig.json - Keep docs check script pointing to the new tsconfig
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 35eff67ece
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Move the stats fetch script next to the docs data it generates and update docs + workflow callsites.
|
@jong-kyung hey there, check the latest commits , added the changes mentioned above! |
|
@codex review |
|
Codex Review: Didn't find any major issues. Hooray! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
jong-kyung
left a comment
jong-kyung
left a comment
There was a problem hiding this comment.
@nozomee Thanks for working through all the feedback — looks great!
Could you resolve the merge conflict with main?
Signed-off-by: deep <sarkarreall@gmail.com>
done! |
|
@jong-kyung @fengmk2 kindly check the changes! Pushed all the updated commits |
Apply vp fmt formatting and fix lint errors flagged by vp check: rename `__dirname` to `currentDir` (no-underscore-dangle) and switch the post-write status log to console.error (no-console allows error).
Other workflows (release, test-vp-create, e2e-test) already pin actions/setup-node to v6.4.0; bump the new trusted-stack-stats workflow to match.
|
#1573 action works, thanks again @nozomee @jong-kyung |
|
Loved working with you both — learned a lot and really appreciated it! 🙌 @fengmk2 @jong-kyung |
5 participants
Changes made
1.
docs/.vitepress/theme/components/home/FeatureCheck.vue600+→750+(text before theESLintcode span).2.
docs/.vitepress/theme/components/home/ProductivityGrid.vue“A trusted stack to standardize on” — Vite
69m+→115m+78.7k→80.4kVitest
35m+→57m+16.1k→16.5kOXC (npm row uses
oxlintpackage downloads)5m+→5.3m+19.8k→21.0kFiles touched: 2
Net: 7 lines updated (string substitutions only; no logic or layout changes).